Procedures for multiple active bandwidth parts

ABSTRACT

Apparatuses, methods, and systems are disclosed for efficient management of multiple active BWPs. One apparatus includes a processor and a transceiver that communicates with a serving cell using multiple active bandwidth parts (“BWPs”) for the serving cell. Here, the serving cell is configured with multiple configured grants, each active BWP configured with one of the multiple configured grants. The processor receives an indication from a base unit of which configured grants are to be used upon a change to the multiple active BWPs and selectively activates a configured grant in response to a change to the multiple active BWPs.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to efficient management ofmultiple active bandwidth parts (“BWPs”) and configured grants.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), Positive-Acknowledgment (“ACK”), BinaryPhase Shift Keying (“BPSK”), Bandwidth Part (“BWP”), Clear ChannelAssessment (“CCA”), Cyclic Prefix (“CP”), Cyclical Redundancy Check(“CRC”), Channel State Information (“CSI”), Common Search Space (“CSS”),Discrete Fourier Transform Spread (“DFTS”), Downlink Control Information(“DCI”), Downlink (“DL”), Downlink Pilot Time Slot (“DwPTS”), EnhancedClear Channel Assessment (“eCCA”), Enhanced Licensed Assisted Access(“eLAA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”),European Telecommunications Standards Institute (“ET SI”), Frame BasedEquipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency DivisionMultiple Access (“FDMA”), Frequency Division Orthogonal Cover Code(“FD-OCC”), Guard Period (“GP”), Hybrid Automatic Repeat Request(“HARQ”), Internet-of-Things (“IoT”), Licensed Assisted Access (“LAA”),Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), Long TermEvolution (“LTE”), Multiple Access (“MA”), Modulation Coding Scheme(“MCS”), Machine Type Communication (“MTC”), Multiple Input MultipleOutput (“MIMO”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Next Generation Node B(“gNB”), Non-Orthogonal Multiple Access (“NOMA”), Orthogonal FrequencyDivision Multiplexing (“OFDM”), Primary Cell (“PCell”), PhysicalBroadcast Channel (“PBCH”), Physical Downlink Control Channel (“PDCCH”),Physical Downlink Shared Channel (“PDSCH”), Pattern Division MultipleAccess (“PDMA”), Physical Hybrid ARQ Indicator Channel (“PHICH”),Physical Random Access Channel (“PRACH”), Physical Resource Block(“PRB”), Physical Uplink Control Channel (“PUCCH”), Physical UplinkShared Channel (“PUSCH”), Quality of Service (“QoS”), Quadrature PhaseShift Keying (“QPSK”), Radio Resource Control (“RRC”), Random AccessProcedure (“RACH”), Random Access Response (“RAR”), Radio NetworkTemporary Identifier (“RNTI”), Reference Signal (“RS”), RemainingMinimum System Information (“RMSI”), Resource Spread Multiple Access(“RSMA”), Round Trip Time (“RTT”), Receive (“RX”), Sparse Code MultipleAccess (“SCMA”), Scheduling Request (“SR”), Single Carrier FrequencyDivision Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), SharedChannel (“SCH”), Signal-to-Interference-Plus-Noise Ratio (“SINK”),System Information Block (“SIB”), Synchronization Signal (“SS”),Supplementary Uplink (“SUL”), Transport Block (“TB”), Transport BlockSize (“TBS”), Time-Division Duplex (“TDD”), Time Division Multiplex(“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), TransmissionTime Interval (“TTI”), Transmit (“TX”), Uplink Control Information(“UCI”), User Entity/Equipment (Mobile Terminal) (“UE”), Uplink (“UL”),Universal Mobile Telecommunications System (“UMTS”), Uplink Pilot TimeSlot (“UpPTS”), Ultra-reliability and Low-latency Communications(“URLLC”), and Worldwide Interoperability for Microwave Access(“WiMAX”). As used herein, “HARQ-ACK” may represent collectively thePositive Acknowledge (“ACK”) and the Negative Acknowledge (“NACK”). ACKmeans that a TB is correctly received while NACK (or NAK) means a TB iserroneously received.

In certain wireless communications networks, such as 5G NR Release 15(“Rel-15”), only one active bandwidth part (“BWP”) at a time. Each BWPhas an associated numerology, i.e. each BWP supports only onenumerology. For cases when UE supports services requiring differentnumerologies, gNB needs to switch between different configured BWP(s).Although future releases may permit more than one active BWP, layer 2procedures and related signaling are undefined for the case of multipleactive BWPs.

BRIEF SUMMARY

Methods are disclosed for efficient management of multiple active BWPs.Apparatuses and systems also perform the functions of the methods. Themethods may also be embodied in one or more computer program productscomprising executable code.

A method for efficient management of multiple active BWPs includescommunicating with a serving cell using multiple active BWPs for theserving cell. Here, the serving cell is configured with multipleconfigured grants, each active BWP configured with one of the multipleconfigured grants. The method includes receiving an indication from abase unit of which configured grants are to be used upon a change to themultiple active BWPs and selectively activating a configured grant inresponse to a change to the multiple active BWPs.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for efficient management of multipleactive BWPs;

FIG. 2 is a block diagram illustrating one embodiment of a networkarchitecture for managing configured grants with multiple BWPs;

FIG. 3 is a block diagram illustrating one embodiment of triggering PHRfor multiple BWPs;

FIG. 4 is a block diagram illustrating one embodiment of a networkarchitecture for mapping a BWP to a HARQ process;

FIG. 5 is a block diagram illustrating one embodiment of MCS tables forefficient management of multiple active BWPs;

FIG. 6 is a block diagram illustrating a user equipment apparatus forefficient management of multiple active BWPs; and

FIG. 7 is a flow chart diagram illustrating one method of efficientmanagement of multiple active BWPs.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object-oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus, orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

Generally, the present disclosure describes systems, methods, andapparatus for efficient management of multiple active BWPs. The variousembodiments described herein applies generally to UL and DLtransmissions. Said transmissions can include PUSCH, PDSCH, PUCCH, SRS,or PRACH transmissions. While some examples are described in terms of ULtransmission, it should be noted that the embodiments are not limited tothe UL direction only but may be also applied to DL operations, once theappropriate changes have been made. While the below description the termgNB may be used for a base station, it is to be understood that otherbase station or radio access nodes, e.g. BS, eNB, AP, etc., may be used.Further, the described procedures are described mainly in the context ofNR (e.g., 3GPP fifth-generation radio access technology). However, thedescribed procedures are also equally applicable to other mobilecommunication systems such as LTE, WiMAX, WLAN, and the like.

To support various requirements of different services (at leastincluding enhanced mobile broadband (“eMBB), ultra-reliable low-latencycommunications (“URLLC”), massive machine type communication (“mMTC”)),5G/NR is envisioned to support different OFDM numerologies (i.e.sub-carrier spacing (“SCS”)) and CP length, in a single framework. Asidentified in TR 38.913, the various use cases/deployment scenarios forNR have diverse requirements in terms of data rates, latency, andcoverage.

For example, eMBB is expected to support peak data rates (20 Gbps fordownlink and 10 Gbps for uplink) and user-experienced data rates in theorder of three times what is offered by IMT-Advanced. On the other hand,in case of URLLC, the tighter requirements are put on ultra-low latency(0.5 ms for UL and DL each for user plane latency) and high reliability(1-10⁻⁵ within 1 ms). Finally, mMTC requires high connection density,large coverage in harsh environments, and extremely long-life batteryfor low cost devices.

Therefore, the OFDM numerology (e.g. subcarrier spacing, OFDM symbolduration, cyclic prefix (CP) duration, number of symbols per schedulinginterval) that is suitable for one use case might not work well foranother. For example, low-latency services may require a shorter symbolduration (and thus larger subcarrier spacing) and/or fewer symbols perscheduling interval (aka, TTI) than an mMTC service. Furthermore,deployment scenarios with large channel delay spreads require a longerCP duration than scenarios with short delay spreads. The subcarrierspacing should be optimized accordingly to retain the similar CPoverhead.

In various embodiments, 5G/NR may support different numerologies acrossdifferent carrier(s) for a given UE as well as different numerologieswithin the same carrier for a given UE, i.e. different OFDM numerologiesare multiplexed in frequency-domain and/or time-domain within the samecarrier or across different carriers. This benefits simultaneous supportof services with vastly different requirements, e.g. ultra-low latencycommunications (short symbols and thus wide subcarrier spacing) and MBMSservices (long symbols to enable long cyclic prefix and thus narrowsubcarrier spacing).

In 5G/NR deployments, transmission and reception may include bothcentimeter- and millimeter-wave bands and higher frequency bands, e.g.from 6 GHz up to 70 GHz. Because (i) UE receive channel bandwidth can besmaller than the carrier bandwidth, (ii) non-contiguous spectrum may beused for one carrier, and (iii) multiple numerologies can be configuredwithin one carrier, bandwidth parts (BWPs) based operation was developedin 5G NR. Each BWP consists of a group of contiguous physical resourceblocks (PRBs) and is associated with a certain numerology (i.e.,subcarrier spacing in OFDM operation) and/or service (e.g., eMBB orURLLC).

To enable Bandwidth adaption, i.e. adapting the size of the bandwidthused for data transmission in a serving cell, on the PCell, the gNBconfigures the UE with UL and DL Bandwidth Part(s) (BWP). To enablebandwidth adaptation on SCells for the case of carrier aggregation, thegNB configures the UE with at least DL BWP(s) (i.e. there may be none inthe UL).

Each BWP consists of a group of contiguous physical resource blocks(“PRBs”) and is associated with a certain numerology (e.g., subcarrierspacing in OFDM operation) and/or service (e.g., eMBB or URLLC). Some ofthe use-cases for BWPs are to support, e.g., reduced UE bandwidthcapability; reduced UE energy consumption by means of bandwidthadaptation; frequency division multiplexing (“FDM”) of differentnumerologies; and non-contiguous spectrum.

In BWP operation, a UE may be configured with one or multiple DL BWPsused for DL reception, and one or multiple UL BWPs used for ULtransmission. For example, in 5G NR Release 15 (“Rel-15”), UE may beconfigured with up to four DL BWPs and up to four UL BWPs in a givenserving cell. The configured DL and UL BWPs with the same BWP index fora serving cell are considered to have the same center frequency locationin TDD operation, but may have distinct frequency locations in FDDoperation (e.g., below 6 GHz) while not necessarily spaced at thefrequency division duplex spacing.

An initial DL BPW is defined as the DL BWP of a serving cell (PCell,PSCell, and/or SCell) which corresponds to control resource set(“CORESET”) for Type0-PDCCH common search space which is used forscheduling reception of the Remaining Minimum System Information(“RMSI”). An initial UL BWP is defined as the UL BWP of a primaryserving cell (PCell or PSCell) on which at least initial random-accessprocedure occurs.

An active DL/UL BWP is defined as the DL/UL BWP on a serving cell onwhich data reception/transmission can occur. The active DL/UL BWP may bethe same as the initial DL/UL BWP. As of 3GPP NR Rel-15, the UE is notexpected to monitor or make measurements on any configured BWP otherthan the active DL/UL BWP.

The active DL/UL BWP can dynamically change. For example, a BWPindicator field in downlink control information (“DCI”) forDL-assignment/UL-grant may be used to indicate which of the configuredDL/UL BWPs are currently active for DL reception/UL transmission. If theactive DL BWP has been unused (e.g., no DCI has been received on that DLBWP) for a long time, then the UE may fall back to a so-called defaultDL BWP, which is either the initial DL BWP or another DL BWP (e.g.,configured by higher-layers).

In paired spectrum, DL and UL can switch BWP independently. In unpairedspectrum, DL and UL switch BWP simultaneously. Switching betweenconfigured BWPs happens by means of a DCI, i.e. PDCCH indicating toswitch to another Bandwidth part, or inactivity timer. When aninactivity timer is configured for a serving cell, the expiry of theinactivity timer associated to that cell switches the active BWP to adefault BWP configured by the network. Switching refers to activatingone or more BWP and deactivating an equal number of BWP.

In 3GPP Rel-15, a Serving Cell may be configured with at most four BWPs,and for an activated Serving Cell, there is always one active BWP at anypoint in time. The BWP switching for a Serving Cell is used to activatean inactive BWP and deactivate an active BWP at a time and is controlledby the PDCCH indicating a downlink assignment or an uplink grant. Uponaddition of SpCell or activation of an SCell, one BWP is initiallyactive without receiving PDCCH indicating a downlink assignment or anuplink grant. This BWP may be referred to as an initial BWP.

On the active BWP for each activated Serving Cell configured with a BWP,the medium access control (“MAC”) entity applies normal operationsincluding: 1) transmit on UL-SCH; 2) transmit on RACH; 3) monitor thePDCCH; 4) transmit PUCCH; 5) receive DL-SCH; and 6) (re-)initialize anysuspended configured uplink grants of configured grant Type 1 accordingto the stored configuration

On the inactive BWP for each activated Serving Cell configured with aBWP, the MAC entity: 1) does not transmit on UL-SCH; 2) does nottransmit on RACH; 3) does not monitor the PDCCH; 4) does not transmitPUCCH; 5) does not receive DL-SCH; 6) clears any configured downlinkassignment and configured uplink grant of configured grant Type 2; and7) suspends any configured uplink grant of configured Type 1.

If the active UL BWP has no PRACH resources configured, the UE, upontriggering of a RACH procedure, switches to the initial DL BWP and ULBWP and performs RACH procedure. If the MAC entity receives a PDCCH forBWP switching while a Random-Access procedure is ongoing in the MACentity, it is up to UE implementation whether to switch BWP or ignorethe PDCCH for BWP switching. If the MAC entity decides to perform BWPswitching, the MAC entity stops the ongoing Random-Access procedure andinitiate a Random-Access procedure on the new activated BWP. If the MACdecides to ignore the PDCCH for BWP switching, the MAC entity continueswith the ongoing Random-Access procedure on the active BWP.

As mentioned before, 3 GPP Rel-15 allows only one active BWP at a time.Each BWP has an associated numerology, i.e. each BWP supports only onenumerology. For cases when UE supports services requiring differentnumerologies, in Rel-15 the gNB needs to switch between differentconfigured BWP(s). In order to support QoS more efficiently, inparticular for scenarios where a UE has services/radio bearer runningrequiring different numerologies, it is envisioned that it will bepossible to have multiple BWP(s) activated simultaneously in futurereleases.

The present disclosure describes several layer 2 procedures and relatedsignaling details in the context of multiple activated BWPs.Specifically, the following procedures are disclosed for supportingmultiple active BWP(s) in a serving cell: Logical channelprioritization/restriction procedure; Uplink power control operation;Pathloss reference determination; Configured grants; HARQ protocoloperation; Maintenance of BWP(s) for UEs in INACTIVE state; Maintenanceof Uplink Time Alignment; and Monitoring of Common Search Space.

FIG. 1 depicts a wireless communication system 100 for UE power controlfor multiple UL carriers, according to embodiments of the disclosure. Inone embodiment, the wireless communication system 100 includes at leastone remote unit 105, a radio access network (“RAN”) 120, and a mobilecore network 140. The RAN 120 and the mobile core network 140 form amobile communication network. The RAN 120 may be composed of a base unit110 with which the remote unit 105 communicates using wirelesscommunication links 115. Even though a specific number of remote units105, base units 110, wireless communication links 115, RANs 120, andmobile core networks 140 are depicted in FIG. 1 , one of skill in theart will recognize that any number of remote units 105, base units 110,wireless communication links 115, RANs 120, and mobile core networks 140may be included in the wireless communication system 100.

In one implementation, the wireless communication system 100 iscompliant with the 5G system specified in the 3GPP specifications. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication network, for example, LTEor WiMAX, among other networks. The present disclosure is not intendedto be limited to the implementation of any particular wirelesscommunication system architecture or protocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas the UEs, subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, userterminals, wireless transmit/receive unit (“WTRU”), a device, or byother terminology used in the art.

The remote units 105 may communicate directly with one or more of thebase units 110 in the RAN 120 via uplink (“UL”) and downlink (“DL”)communication signals. Furthermore, the UL and DL communication signalsmay be carried over the wireless communication links 115. Here, the RAN120 is an intermediate network that provides the remote units 105 withaccess to the mobile core network 140.

In some embodiments, the remote units 105 communicate with anapplication server 135 via a network connection with the mobile corenetwork 140. For example, an application 107 (e.g., web browser, mediaclient, telephone/VoIP application) in a remote unit 105 may trigger theremote unit 105 to establish a PDU session (or other data connection)with the mobile core network 140 via the RAN 120. The mobile corenetwork 140 then relays traffic between the remote unit 105 and theapplication server 135 in the packet data network 130 using the PDUsession. Note that the remote unit 105 may establish one or more PDUsessions (or other data connections) with the mobile core network 140.As such, the remote unit 105 may concurrently have at least one PDUsession for communicating with the packet data network 130 and at leastone PDU session for communicating with another data network (not shown).

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as anaccess terminal, an access point, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, or by any other terminologyused in the art. The base units 110 are generally part of a radio accessnetwork (“RAN”), such as the RAN 120, that may include one or morecontrollers communicably coupled to one or more corresponding base units110. These and other elements of radio access network are notillustrated but are well known generally by those having ordinary skillin the art. The base units 110 connect to the mobile core network 140via the RAN 120.

The base units 110 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector, via a wirelesscommunication link 115. The base units 110 may communicate directly withone or more of the remote units 105 via communication signals.Generally, the base units 110 transmit DL communication signals to servethe remote units 105 in the time, frequency, and/or spatial domain.Furthermore, the DL communication signals may be carried over thewireless communication links 115. The wireless communication links 115may be any suitable carrier in licensed or unlicensed radio spectrum.The wireless communication links 115 facilitate communication betweenone or more of the remote units 105 and/or one or more of the base units110.

In one embodiment, the mobile core network 140 is a 5G core (“5GC”) orthe evolved packet core (“EPC”), which may be coupled to a packet datanetwork 130, like the Internet and private data networks, among otherdata networks. A remote unit 105 may have a subscription or otheraccount with the mobile core network 140. Each mobile core network 140belongs to a single public land mobile network (“PLMN”). The presentdisclosure is not intended to be limited to the implementation of anyparticular wireless communication system architecture or protocol.

The mobile core network 140 includes several network functions (“NFs”).As depicted, the mobile core network 140 includes multiple user planefunctions (“UPFs”) 145. The mobile core network 140 also includesmultiple control plane functions including, but not limited to, anAccess and Mobility Management Function (“AMF”) 141 that serves the RAN120, a Session Management Function (“SMF”) 143, and a Policy ControlFunction (“PCF”) 147. In certain embodiments, the mobile core network140 may also include an Authentication Server Function (“AUSF”), aUnified Data Management function (“UDM”) 149, a Network RepositoryFunction (“NRF”) (used by the various NFs to discover and communicatewith each other over APIs), or other NFs defined for the 5GC.

Although specific numbers and types of network functions are depicted inFIG. 1 , one of skill in the art will recognize that any number and typeof network functions may be included in the mobile core network 140.Moreover, where the mobile core network 140 is an EPC, the depictednetwork functions may be replaced with appropriate EPC entities, such asan MME, S-GW, P-GW, HSS, and the like. In certain embodiments, themobile core network 140 may include a AAA server.

In various embodiments, the mobile core network 140 supports differenttypes of mobile data connections and different types of network slices,wherein each mobile data connection utilizes a specific network slice.Here, a “network slice” refers to a portion of the mobile core network140 optimized for a certain traffic type or communication service. Incertain embodiments, the various network slices may include separateinstances of network functions, such as the SMF 143 and UPF 145. In someembodiments, the different network slices may share some common networkfunctions, such as the AMF 141. The different network slices are notshown in FIG. 1 for ease of illustration, but their support is assumed.

While FIG. 1 depicts components of a 5G RAN and a 5G core network, thedescribed embodiments for UE power control for multiple UL carriersapply to other types of communication networks, including IEEE 802.11variants, UMTS, LTE variants, CDMA 2000, Bluetooth, and the like. Forexample, in an LTE/EPC variant, the AMF 141 may be mapped to an MME, theSMF 143 may be mapped to a control plane portion of a PGW, the UPF 145may be mapped to a STW and a user plane portion of the PGW, etc.

The remote unit 105 may be configured for BWP operation by the base unit110. AS described above, the remote unit 105 may be configured withmultiple BWP on both the UL and DL. In various embodiments, the remoteunit 105 may perform uplink transmission on one or multiple active ULBWPs using the procedures described herein. Additionally, the remoteunit 105 may perform DL reception on one or multiple active DL BWPsusing the procedures described herein. The UL and DL transmissions mayinclude PUSCH, PDSCH, PUCCH, SRS, or PRACH transmissions.

FIG. 2 depicts a network architecture 200 for efficient management ofmultiple active BWPs, according to embodiments of the disclosure. Thenetwork architecture 200 includes a UE 205 and a RAN Node 210. The UE205 may be one embodiment of the remote unit 105, described above. TheRAN Node 210 (e.g., a gNB) may be one embodiment of the base unit 110,described above.

As depicted, the RAN Node 210 may configure the UE 205 with multiple ULBWP (see messaging 215). Additionally, the RAN Node 210 may configureone or more configured grants (e.g., semi-static grants) (see messaging220). There are two types of transmission without dynamic grant definedfor NR: Type 1 and Type 2. With configured grant Type 1, an uplink grantis provided by RRC and stored as configured uplink grant. Withconfigured grant Type 2, an uplink grant is provided by PDCCH, andstored (or cleared) as configured uplink grant based on L1 signalingindicating configured grant activation or deactivation.

Type 1 and Type 2 configured grants (e.g., semi-static grants) may beconfigured by RRC per Serving Cell and per BWP. In some embodiments,multiple configurations may be active simultaneously only on differentServing Cells. For Type 2 grants, activation and deactivation may beindependent among the Serving Cells. For the same Serving Cell, the MACentity may be configured with either a Type 1 grant or Type 2 grant.While following descriptions are refer mostly to configured grant Type1, in various embodiments, the configured uplink grant may be Type 2.

In order to allow service continuity when switching BWPs, the RAN Node210 configures on all configured BWPs of a UE (e.g., a remote unit 105)the same configured grant allocation, thus the same periodicity, sametimeDomainOffset parameter (Offset of a resource with respect to SFN=0in time domain), etc. Beneficially, in case of BWP switching, theconfigured grant is implicitly activated on the newly activated BWP andlogical channels (“LCHs”) configured for the configured grant can usethe allocated resources.

In various embodiments, it may be desirable to avoid the situation thatmultiple configured grant (“CG”) configurations are active at the sametime. Assuming that UE supports only one active configured grant (“CG”)configuration per serving cell and the same CG configuration may be usedfor all configured BWP(s) in a serving cell. Accordingly, the RAN Node210 (a network entity “NE,” such as gNB, base unit 110, or othersuitable base station) indicates an activation/deactivation status forthe CG allocations (see messaging 225). The UE 205 then selectivelyactivate (or deactivates) the CG allocations upon BWP activation,deactivation, or switching (see block 230).

According to some embodiments, the RAN Node 210 explicitly signals whichof the configured grant allocations (e.g. configured grant type 1allocations) configured for the different BWP(s) of a serving cell isactivated and, respectively, which are deactivated. In certainembodiments, MAC control signaling is used for such an indication, i.e.,signaling the activation/deactivation status of a CG. In one embodiment,a new MAC control element (“CE”) is introduced which contains a bitmap,each bit of the bitmap representing the activation/deactivation statusof a configured grant allocation. According to one implementation, a bitof the bitmap set to ‘1’ indicates the UE is to activate thecorresponding configured grant allocation while a bit of the bitmap setto ‘0’ indicates the UE is to deactivate the corresponding configuredgrant allocation. In certain embodiments, the MAC CE indicates theactivation/deactivation status of the configured grant(s) for the BWP(s)configured for a serving cell. In a further embodiment, the MAC CE maycontain a serving cell identifier field identifying the serving cell forwhich the configured grant(s) activation/deactivation status representedby the bitmap is signaled.

In various embodiments, the activation/deactivation indication of aconfigured grant allocation is signaled together with theactivation/deactivation/switching signaling of the corresponding BWP. Inone embodiment the RAN Node 210, such as gNB or base unit 110, indicatesto the UE 205 whether it is to activate the corresponding configuredgrant (if configured) when activating a BWP. Here, activating thecorresponding configured grant may include initializing (orre-initializing) any suspended configured uplink grant(s) of configuredgrant Type 1 according to the stored configuration.

In some embodiments, the activation/deactivation status of a configuredgrant may be represented by a one-bit flag within theactivation/deactivation/switching BWP signaling. According to oneimplementation, setting the one-bit flag set ‘1’ directs the UE toactivate the corresponding configured grant (if configured), e.g.,(re-)initialize the suspended configured uplink grant(s) of configuredgrant Type 1 according to the stored configuration. In certainembodiments, said BWP activation/deactivation/switching signaling may bedone by physical layer signaling (e.g., within a DCI) or MAC signaling(e.g., MAC CE).

According to various embodiments, there may be multiple configuredgrant(s) in a serving cell active at the same time. In certainembodiments, the RAN Node 210 signals the activation/deactivation statusof a configured grant (e.g., type 1 CG) configured for a serving cell,e.g., on a BWP configured for a serving cell. In one implementation, theactivation/deactivation status of a configured grant is signaled bymeans of a bitmap, each bit of the bitmap representing theactivation/deactivation of one configured grant of the serving cell.

FIG. 3 depicts a procedure 300 for UE power control for multiple ULcarriers, according to embodiments of the disclosure. The procedure 300may be performed by a UE, such as the remote unit 105 and/or the UE 205.Here, the UE is configured with multiple BWPs for a UL carrier (e.g., ofa serving cell).

The procedure 300 begins as the UE monitors a power headroom reportingtimer, such as ‘phr-ProhibitTimer’, to determine whether the timer isexpired (see decision block 305). If the timer expires, then the UEtriggers a PHR if a pathloss has changed more than a threshold amount(e.g., indicated by phr-Tx-PowerFactorChange parameter) for at least onemonitored UL BWP (see block 315). Additionally, the UE monitors for aswitch in BWP (see decision block 310). If a BWP switch occurs, then theUE triggers a PHR if a pathloss has changed more than a threshold amount(e.g., indicated by phr-Tx-PowerFactorChange parameter) for at least onemonitored UL BWP (see block 315).

Fifth-generation (“5G”) mobile networks may implement various powercontrol (“PC”) and power headroom (“PH”) formulas that involve someaspects of BWP operation. In particular, many PC parameters areconfigured per UL BWP, including, but not limited to, the UE-specificcomponent of target power spectral density (“PSD”) value Po_UE, thefractional pathloss (“PL”) compensation factor α, the PL reference, theclosed-loop power control (“CL-PC”) process, and the transmissionbandwidth (i.e., number of PRBs) allocation.

A power headroom report (“PHR”) is triggered, and subsequently sent,when certain trigger conditions are met. One of those trigger conditionsis related to a change in the pathloss, i.e. the path loss has changedmore than phr-Tx-PowerFactorChange dB since the last transmission of aPHR in this MAC entity. In one embodiment, pathloss trigger condition ischecked by the UE 205 for every active UL BWP or a subset of the activeUL BWP(s), the subset being, e.g., configured by the RAN node 210.

According to certain embodiments, a PHR may be triggered 315 when thephr-ProhibitTimer expires (or has expired, refer to decision block 305)and the path loss has changed more than phr-Tx-PowerFactorChange dB forat least one active UL BWP of a serving cell. Alternatively, a PHR maybe triggered when the phr-ProhibitTimer expires (or has expired, seedecision 305) and the path loss has changed morethanphr-Tx-PowerFactorChange dB for at least one active UL BWP of thesubset of active UL BWP(s) of any MAC entity which is used as a pathlossreference since the last transmission of a PHR in this MAC entity whenthe MAC entity has UL resources for new transmission.

In certain embodiments, when deactivating an active BWP and activatinganother BWP in a serving cell at the same time, referred to herein asBWP “switching”, the UE 205 checks the PHR pathloss trigger conditionacross the BWP switch (refer to decision block 310). In other words, theUE 205 may compare pathloss measurements done on the old BWP withpathloss measurements on the newly activated BWP (after switching) andtrigger a PHR when pathloss has changed more thanphr-Tx-PowerFactorChange dB between the old BWP and new BWP.

In one embodiment, the UE 205 is not required to report PH informationfor an active (UL) BWP in case the BWP was activated after the UE 205started the generation of the TB containing the PHR MAC CE. Theassumption here is that the UE 205 reports PH information for everyactivated UL BWP in a serving cell. However, due to processing timingconstraints, the UE 205 may not be able to calculate/report the powerheadroom level for an activated UL BWP in a situation where the controlsignaling activating said UL BWP is received after the time instancewhere the UE 205 received an UL grant for an initial PUSCH transmission,the PUSCH transmission carrying a PHR MAC CE.

Power control and power headroom formulas that involve some aspects ofBWP operation have been adopted for 5G operation. For example, if a UEtransmits a PUSCH on UL BWP b of UL carrier f of serving cell c usingparameter set configuration with index j and PUSCH power controladjustment state with index l, the UE determines the PUSCH transmissionpower P_(PUSCH,b,f,c)(i,j,q_(d),l) in PUSCH transmission occasion i as

                 Equation  1${P_{{PUSCH},b,f,c}( {i,j,q_{d},l} )} = {\min\begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\_ PUSCH},b,f,c}(j)} + {10{\log_{10}( {2^{\mu} \cdot {M_{{RB},b,f,c}^{PUSCH}(i)}} )}} + {{\alpha_{b,f,c}(j)} \cdot {{PL}_{b,f,c}( q_{d} )}} + {\Delta_{{TF},b,f,c}(i)} + {f_{b,f,c}( {i,l} )}}\end{Bmatrix}}$

where the PUSCH transmission power of Equation 1 is in [dBm], where allparameters in the calculation are defined in 3GPP TS 38.213 (ver.15.0.0), which is incorporated herein by reference.

Many PC parameters are configured per UL BWP, including: the UE-specificcomponent of target power spectral density (“PSD”) value ‘P0_UE’, thefractional pathloss compensation factor α, the pathloss (“PL”)reference, the closed-loop power control (“CL-PC”) process, and thetransmission bandwidth (e.g., number of PRBs) allocation. However, theconfigured maximum UE transmit power, ‘P_(CMAX),f,c,’ may be configuredper UL carrier of a serving cell, without regard to the choice of ULBWP.

Furthermore, the UE 205 may be configured with somepathlossReferenceLinking parameter 325, for example as depicted in theServingCellConfig Information Element 320. The value 330 of thepathlossReferenceLinking parameter 325 indicates whether the UE 205 isto use either the downlink PCell or the downlink SCell as the pathlossreference serving cell.

According to one embodiment, the UE 205 uses the reference signal (“RS”)index q_(d) of the current active UL BWP of the reference serving cell(either PCell or corresponding SCell) for calculating the pathlossestimate. For example, if the pathlossReferenceLinking is set to Pcellfor a serving cell of the UE 205, then the UE 205 uses the RS indexq_(d) of the current active UL BWP of the PCell for pathloss estimatesused in this serving cell for power control related operations such ase.g. determination of transmission for UL transmission (e.g., PUSCH,PUCCH, or SRS). For example, in case the pathlossReferenceLinking IE isset to ‘PCell’ for an SCell of the UE 205, e.g., uses for thedetermination of the PUSCH transmission power or for the calculation ofa PHR for this SCell the PUSCH-PathlossReferenceRS of the current activeUL BWP of PCell.

In another embodiment, the UE 205 uses the RS index q_(d) of the currentactive DL BWP of the reference serving cell (either PCell orcorresponding SCell) for calculating the pathloss estimate. For examplein case the pathlossReferenceLinking is set to PCell for a serving cellof the UE 205, the UE 205 uses the RS index q_(d) of the current activeDL BWP of the PCell for pathloss estimates used in this serving cell forpower control related operations such as e.g. determination oftransmission for PUSCH/PUCCH/SRS. For example, in case thepathlossReferenceLinking IE is set to PCell for an SCell of the UE 205,the UE 205 may then use the PUSCH-PathlossReferenceRS of the currentactive DL BWP of PCell for the determination of the PUSCH transmissionpower or for the calculation of a PHR for this SCell, i.e., paired DLBWP is the current active DL BWP.

For cases when there are more than one active DL/UL BWP(s) in a servingcell, several possibilities exist for which of the current active UL/DLBWPs of the pathloss reference serving cell (DL PCell, correspondingSCell DL) the UE 205 is to use the RS index q_(d) for the estimation ofthe path-loss. In some embodiments, the UE 205 selects a DL BWP that islinked (or paired) to the UL BWP b and then calculates the downlinkpath-loss estimate using RS index q_(d) of the selected DL BWP.

In one example, the linked/paired DL BWP b for which a downlinkpath-loss estimate is calculated is the initial DL BWP within thereference serving cell, i.e., DL PCell or corresponding DL SCell.

In one example, the linked/paired DL BWP b for which a downlinkpath-loss estimate is calculated is the default DL BWP within thereference serving cell (either DL PCell or corresponding DL SCell). Notethat in one embodiment the default DL BWP is the same as the initial DLBWP. In other embodiments, the default DL BWP is a different DL BWP thanthe initial DL BWP.

In certain embodiments, there may be an explicit linking or implicitlinking (e.g., UL BWP and DL BWP with the same BWP index are linked)between a DL BWP and UL BWP for the pathloss estimate, i.e., in case theUE 205 needs to estimate the pathloss for a power control relatedoperation for uplink BWP b, e.g., determination of PUSCH TX power, thepathloss Reference signals (RS) indicated by the RS index q_(d) of thelinked DL BWP in the reference serving cell (either PCell or SCell) areused for the pathloss estimation. Such explicit linking/pairing may beaccording to certain embodiments configured by higher layer signaling.

In one example, the linked/paired DL BWP b for which a downlinkpath-loss estimate is calculated is the DL BWP with a predefinedBWPindex, i.e. BWP with BWPindex=0.

In one example, the linked/paired DL BWP b for which a downlinkpath-loss estimate is calculated is the active DL BWP in the referenceserving cell with the lowest BWPindex (among the active DL BWPs in thereference serving cell).

According to one embodiment, the UE 205 releases all dedicated BWPsconfigured for a serving cell except one BWP, e.g. the initial BWP oralternatively the default BWP, when being directed to the Inactive statefrom the NR. Alternatively, and according to another embodiment, the UE205 deactivates all configured BWP(s) of a serving cell except one BWP,e.g. the initial BWP or alternatively the default BWP, when beingdirected to the Inactive state from the NR. Here, the resume proceduremay only take place on the initial or default BWP, e.g., the UE 205performing RACH procedure for resuming to either RRC connected state ordata transmission without transiting to RRC connected state.

FIG. 4 depicts a network architecture 400 for efficient management ofmultiple active BWPs, according to embodiments of the disclosure. Thenetwork architecture 400 includes the UE 205 and the RAN Node 210. Asdepicted, the RAN Node 210 may configure the UE 205 with multiple UL BWPfor a serving cell (see messaging 405). Additionally, the RAN Node 210may indicate a BWP-to-HARQ entity mapping (see messaging 410), asdiscussed in further detail below.

In various embodiments, the MAC entity on the UE 205 may include oneHARQ entity for each active BWP of a serving cell. This ensures parallelHARQ operation within and across all active BWPs, i.e., each active BWPis operated independently. In certain embodiments, a MAC entity mayinclude one HARQ entity per serving cell (including the case where asupplemental UL carrier is configured for a serving cell), becauseRel-15 supports only one active BWP at a time per serving cell. Here,each HARQ entity maintains a number of parallel HARQ processes. In oneembodiment, the number of parallel HARQ processes per HARQ entity may befixed by industry standard (e.g., 3GPP specification).

In some embodiments, one HARQ entity may be shared by more than one(active) BWP(s) of a serving cell. Here, the HARQ processes of the HARQentity are used for transmissions/receptions on the more than one activeBWP(s). In one embodiment, the RAN Node 210 configures and signals themapping between BWP and HARQ entity. According to certain embodiments,this mapping between BWP and HARQ entity may be different for DL and ULHARQ protocol operation. In an alternative embodiment, the DCI, i.e. DLor UL grant, contains a HARQ entity ID in addition to the HARQ processID. The DCI based signaling would obviate the mapping configurationbetween BWP and HARQ entity.

In other embodiments, the MAC entity may include one HARQ entity for allBWP(s) of a serving cell, even for the case that multiple BWPs areactive at the same time. In such embodiments, number of HARQ processesof the HARQ entity may be increased compared to Rel-15, where only oneBWP can be active at one time. Here, the HARQ processes can be used fortransmission/receptions across all active BWPs. In one embodiment a HARQ(re)transmission of the same TB may occur on different BWPs. Forexample, an initial transmission for HARQ process ID=1 may be scheduledon BWP ID=1, whereas the retransmission for HARQ process ID=1 may bescheduled on BWP ID=2.

In one embodiment, when the RAN Node 210 switches a BWP, i.e. signalsthe UE 205 to activate an inactive BWP and deactivate an active BWP atthe same time, the HARQ protocol operation continues across the twoBWPs. For example, the HARQ protocol states and HARQ buffer remains thesame (e.g., is not changed) upon the BWP switch. In another embodiment,the UE 205 resets the HARQ protocol operation in response to a BWPswitch. For example, the UE 205 may flush the HARQ buffer andre-initialize the HARQ protocol states/timers upon the BWP switch. Incertain embodiments, the control signaling indicating a BWP switch (e.g.DCI) contains a field indicating whether the HARQ buffer should beflushed and/or HARQ protocol reset/initialization should be applied.

As mentioned above, one motivation for activating multiple BWPs at thesame time is to support multiple numerologies, thereby supportingdifferent services like eMBB and URLLC being operated on different BWPssimultaneously. FIG. 5 depicts one example 500 of different servicesbeing operated on different BWPs simultaneously. Here, a first BWP 505supports a first service (depicted here as eMBB service 515) and asecond BWP 510 supports a second service (depicted here as URLLC service520). Moreover, each service is associated with an MCS table,specifically a first MCS table 525 for the eMBB service 515, and asecond MCS table 530 for the URLLC service 520.

As depicted, a different MCS table (e.g., used to achieve a BLERoperation point) may be used for URLLC than for eMBB, due to thedifferent natures of the services. Note that the focus of current URLLCdevelopment is on latency of the service. One option of operatingmultiple active BWPs is to associate specific services with BWPs, suchthat eMBB and URLLC services are not supported in the same BWP, asdepicted in FIG. 5 . If the current restriction parameters (SCS, maximumPUSCH duration, configured grant type 1, and allowed cells) used in theLCP procedure are not enough to distinguish a URLLC and eMBB grant, thenaccording to one embodiment, a mapping between LCH and BWP may be usedintroduced. Here, only certain LCH may be allowed to use UL resources ona specific BWP, as defined via the mapping. During LCP procedure, thisfurther restriction (the mapping restriction between LCH and BWP) is tobe considered by the UE 205.

For the case of having multiple active BWPs, duplication may besupported by using two BWPs of a serving cell. In certain embodiments,the two BWPs are far away from each other in the serving cell'sfrequency band, e.g., at the outer edges of the serving cell. This wouldalso allow performing duplication in a non-CA case. Moreover, the RANNode 210 may configure the BWP restriction for a duplication bearer,i.e. bearer which is configured for duplication. Additionally, the RANNode 210 may configure which BWP(s) are allowed for the LCHs used for aduplication radio bearer.

In case of having multiple active BWPs, it may happen that the UE 205 isconfigured with multiple CSS, i.e. there may be one CSS per BWP. In suchembodiments, the UE 205 may be configured to only monitor one CSS.Moreover, the UE 205 may be configured with a rule or policy as to whichCSS the UE 205 is to monitor. For example, the UE 205 may be configuredto monitor only the CSS associated with a primary BWP. In oneembodiment, the network (e.g., via RAN Node 210) configures the UE 205to monitor only a single CSS. In another embodiment, the UE 205 may bepreconfigured with the rule/policy indicating which CSS the UE 205 is tomonitor.

In NR, a UE 205 may be configured with up to 4 UL BWP(s) for a servingcell. The BWP concept allows for power savings in the UE 205 by adaptingthe RX/TX bandwidth. Because each BWP is associated with one OFDMnumerology (e.g., subcarrier spacing (“SCS”)), different BWP(s) within acarrier/serving cell may use a different timing advance (“TA”)granularity depending on the associated SCS. Given a certain OFDMnumerology, the RAN Node 210 may maintain the TA granularitysignificantly finer than the length of the corresponding CP length.Because the CP length in different numerology is scaled with the 15 kHzcase, the scaled timing advance granularity may be used for differentnumerology.

According to one embodiment, different BWPs of a serving cell may beassociated with a different TA group (“TAG”). In various embodiments,different BWP(s) of a serving cell are associated with different TRPs,which in turn means that uplink transmissions on different BWPs of aserving cell may require a different timing alignment value. When the UE205 is scheduled for an uplink transmission on a certain UL BWP of aserving cell, the UE 205 is to use the timing advance value associatedwith this BWP. A UE 205 may have to maintain multiple TA loops for oneserving cell, i.e. for each TAG associated with a BWP of a serving cell,UE 205 has to maintain a TA process/loop.

FIG. 6 depicts a user equipment apparatus 600 that may be used for UEpower control for multiple UL carriers, according to embodiments of thedisclosure. The user equipment apparatus 600 may be one embodiment ofthe remote unit 105, described above. Furthermore, the user equipmentapparatus 600 may include a processor 605, a memory 610, an input device615, an output device 620, a transceiver 625 for communicating with oneor more base units 110.

As depicted, the transceiver 625 may include a transmitter 630 and areceiver 635. The transceiver 625 may also support one or more networkinterfaces 640, such as the Uu interface used to communicate with a gNB,or another suitable interface for communicating with the RAN 120. Invarious embodiments, the transceiver 625 receives configuration of aplurality of uplink carriers for a serving cell. In some embodiments,the transceiver 625 receives configuration of a first number of uplinkcarriers of the plurality of uplink carriers, the first number of uplinkcarriers corresponding to a first number of configured and active uplinkbandwidth parts of a first uplink carrier of the serving cell.

In some embodiments, the input device 615 and the output device 620 arecombined into a single device, such as a touchscreen. In certainembodiments, the user equipment apparatus 600 may not include any inputdevice 615 and/or output device 620.

The processor 605, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 605 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 605 executes instructions stored in thememory 610 to perform the methods and routines described herein. Theprocessor 605 is communicatively coupled to the memory 610, the inputdevice 615, the output device 620, and the transceiver 625.

In various embodiments, the transceiver 625 communicates with a servingcell using multiple active BWPs for the serving cell. Here, the servingcell may be configured with multiple configured grants, each active BWPconfigured with one of the multiple configured grants. In certainembodiments, a number of active BWPs is greater than a number ofactivated configured grants.

In certain embodiments, the multiple active BWPs are selected from a setof configured BWPs of the serving cell. In such embodiments, theprocessor 605 may map one or more logical channels to each of themultiple configured BWPs and prioritizing data from the logical channelsfor transmission on an uplink BWP. In some embodiments, the userequipment apparatus 600 supports a plurality of services, each serviceassociated with a different active BWP.

The processor 605 receives (e.g., via the transceiver 625) an indicationfrom a base unit (e.g., base unit 110 and/or RAN node 210) of whichconfigured grants are to be used upon a change to the multiple activeBWPs. In some embodiments, the indication is received in a MAC CE. Insuch embodiments, the MAC CE may include a bitmap. Here, each bit of thebitmap may indicate whether a configured grant is to be activated ordeactivated.

In some embodiments, the transceiver 625 receives an indication toswitch an active BWP, wherein the indication to switch an active BWP andthe indication of which configured grants are to be used are included inthe same message.

In response to change to the multiple active BWPs, the processor 605selectively activates (and/or selectively deactivates) one or more ofthe multiple configured grants (e.g., based on the indication). Invarious embodiments, the change to the multiple active BWPs is theactivation of a BWP, the deactivation of a BWP, or the switching of anactive BWP of the serving cell. In some embodiments, the transceiver 625receives an indication to transition to an inactive state. In suchembodiments, the processor 605 deactivates all active BWPs of theserving cell except a single BWP, the single BWP being one of an initialBWP and a default BWP.

In certain embodiments, the change to the multiple active BWPs comprisesswitching a first BWP for a second BWP. In such embodiments, theprocessor 605 may continue HARQ protocol operation across the first andsecond BWPs. In certain embodiments, different ones of the active BWPsare associated with different timing advance groups. In suchembodiments, the processor 605 may maintain multiple timing advanceloops for the serving cell, each timing advance loop associated with adifferent one of the timing advance groups.

In some embodiments, the processor 605 may check a pathloss triggercondition in response to the change to the multiple active BWPs andreport power headroom information for each of the multiple active BWPs.In such embodiments, checking the pathloss trigger condition in responseto the change to the multiple active BWPs comprises checking a pathlosstrigger condition for subset of the active BWPs.

In certain embodiments, the change to the multiple active BWPs includesswitching a first BWP for second BWP. In such embodiments, checking thepathloss trigger condition in response to the change to the multipleactive BWPs may include: taking a first pathloss measurement on thefirst BWP, taking a second pathloss measurement on the second BWP,calculating a pathloss difference using the first pathloss measurementto the second pathloss measurement, and triggering a power headroomreport if the path loss difference is more than a threshold amount.

In some embodiments, the serving cell is a reference serving cell. Insuch embodiments, the transceiver 625 may receive a pathloss referencelinking parameter that links an active downlink BWP to an active uplinkBWP, wherein the processor 605 estimates a pathloss value for the activeuplink BWP using the linked active downlink BWP. In certain embodiments,the linked active downlink BWP is one of an initially active downlinkBWP within the reference serving cell and a default downlink BWP withinthe reference serving cell.

In certain embodiments, the processor 605 configures a HARQ entity foreach active BWP of the serving cell, each HARQ entity maintaining a setof parallel HARQ processes. In some embodiments, the processor 605configures a single HARQ entity for all active BWP of the serving cell.In such embodiments, the single HARQ entity is associated with aplurality of HARQ processes, wherein the plurality of HARQ processes areshared across the active BWPs.

The memory 610, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 610 includes volatile computerstorage media. For example, the memory 610 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 610 includes non-volatilecomputer storage media. For example, the memory 610 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 610 includes bothvolatile and non-volatile computer storage media.

In some embodiments, the memory 610 stores data related to efficientmanagement of multiple active BWPs. For example, the memory 610 maystore BWP configurations, configured grant allocations, power controlparameters, configuration and activation/deactivation status for servingcells and/or BWPs, and the like. In certain embodiments, the memory 610also stores program code and related data, such as an operating systemor other controller algorithms operating on the remote unit 105.

The input device 615, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 615 maybe integrated with the output device 620, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 615 includes a touchscreen such that text may be input using avirtual keyboard displayed on the touchscreen and/or by handwriting onthe touchscreen. In some embodiments, the input device 615 includes twoor more different devices, such as a keyboard and a touch panel.

The output device 620, in one embodiment, is designed to output visual,audible, and/or haptic signals. In some embodiments, the output device620 includes an electronically controllable display or display devicecapable of outputting visual data to a user. For example, the outputdevice 620 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user. As another,non-limiting, example, the output device 620 may include a wearabledisplay separate from, but communicatively coupled to, the rest of theuser equipment apparatus 600, such as a smart watch, smart glasses, aheads-up display, or the like. Further, the output device 620 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the output device 620 includes one or morespeakers for producing sound. For example, the output device 620 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 620 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 620 may beintegrated with the input device 615. For example, the input device 615and output device 620 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 620 may be located nearthe input device 615.

The transceiver 625 includes at least transmitter 630 and at least onereceiver 635. One or more transmitters 630 may be used to provide ULcommunication signals to a base unit 110. Similarly, one or morereceivers 635 may be used to receive DL communication signals from thebase unit 110, as described herein. Although only one transmitter 630and one receiver 635 are illustrated, the user equipment apparatus 600may have any suitable number of transmitters 630 and receivers 635.Further, the transmitter(s) 630 and the receiver(s) 635 may be anysuitable type of transmitters and receivers. In one embodiment, thetransceiver 625 includes a first transmitter/receiver pair used tocommunicate with a mobile communication network over licensed radiospectrum and a second transmitter/receiver pair used to communicate witha mobile communication network over unlicensed radio spectrum.

FIG. 7 is a schematic flow chart diagram illustrating one embodiment ofa method 700 for efficient management of multiple active BWPs, accordingto embodiments of the disclosure. In some embodiments, the method 700 isperformed by a UE, such as the remote unit 105, the UE 205, and/or theuser equipment apparatus 600. In certain embodiments, the method 700 maybe performed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 700 begins and communicates 705 with a serving cell usingmultiple active bandwidth parts (“BWPs”) for the serving cell. Here, theserving cell is configured with multiple configured grants, each activeBWP configured with one of the multiple configured grants.

The method 700 includes receiving 710 an indication from a base unit ofwhich configured grants are to be used upon a change to the multipleactive BWPs. The method 700 includes selectively activating 715 aconfigured grant in response to a change to the multiple active BWPs.Here, selectively activating 715 a configured grant may includeactivating or deactivating one or more configured grants. The method 700ends.

Disclosed herein is a first apparatus for efficient management ofmultiple active BWPs. The first apparatus may be implemented by theremote unit 105, the UE 205, and/or the user equipment apparatus 600.The first apparatus includes a processor and a transceiver thatcommunicates with a serving cell using multiple active BWPs for theserving cell. Here, the serving cell is configured with multipleconfigured grants, each active BWP configured with one of the multipleconfigured grants. The processor receives an indication from a base unitof which configured grants are to be used upon a change to the multipleactive BWPs and selectively activates a configured grant in response toa change to the multiple active BWPs.

In some embodiments of the first apparatus, the indication is receivedin a MAC CE. In such embodiments, the MAC CE may include a bitmap. Here,each bit of the bitmap may indicate whether a configured grant is to beactivated or deactivated. In certain embodiments of the first apparatus,a number of active BWPs is greater than a number of activated configuredgrants. In some embodiments of the first apparatus, the transceiverreceives an indication to transition to an inactive state. In suchembodiments, the processor deactivates all active BWPs of the servingcell except a single BWP, the single BWP being one of an initial BWP anda default BWP.

In various embodiments of the first apparatus, the change to themultiple active BWPs is the activation of a BWP, the deactivation of aBWP, or the switching of an active BWP of the serving cell. In someembodiments of the first apparatus, the transceiver receives anindication to switch an active BWP, wherein the indication to switch anactive BWP and the indication of which configured grants are to be usedare included in the same message.

In some embodiments, the first apparatus supports a plurality ofservices, each service associated with a different active BWP. Incertain embodiments of the first apparatus, the multiple active BWPs areselected from a set of configured BWPs of the serving cell. In suchembodiments, the processor may map one or more logical channels to eachof the multiple configured BWPs and prioritizing data from the logicalchannels for transmission on an uplink BWP.

In some embodiments of the first apparatus, the processor may check apathloss trigger condition in response to the change to the multipleactive BWPs and report power headroom information for each of themultiple active BWPs. In such embodiments, checking the pathloss triggercondition in response to the change to the multiple active BWPscomprises checking a pathloss trigger condition for subset of the activeBWPs.

In certain embodiments, the change to the multiple active BWPs includesswitching a first BWP for second BWP. In such embodiments, checking thepathloss trigger condition in response to the change to the multipleactive BWPs may include: taking a first pathloss measurement on thefirst BWP, taking a second pathloss measurement on the second BWP,calculating a pathloss difference using the first pathloss measurementto the second pathloss measurement, and triggering a power headroomreport if the path loss difference is more than a threshold amount.

In some embodiments of the first apparatus, the serving cell is areference serving cell. In such embodiments, the transceiver may receivea pathloss reference linking parameter that links an active downlink BWPto an active uplink BWP, wherein the processor estimates a pathlossvalue for the active uplink BWP using the linked active downlink BWP. Incertain embodiments, the linked active downlink BWP is one of aninitially active downlink BWP within the reference serving cell and adefault downlink BWP within the reference serving cell.

In certain embodiments of the first apparatus, the processor configuresa HARQ entity for each active BWP of the serving cell, each HARQ entitymaintaining a set of parallel HARQ processes. In some embodiments of thefirst apparatus, the processor configures a single HARQ entity for allactive BWP of the serving cell. In such embodiments, the single HARQentity is associated with a plurality of HARQ processes, wherein theplurality of HARQ processes are shared across the active BWPs.

In certain embodiments of the first apparatus, the change to themultiple active BWPs comprises switching a first BWP for a second BWP.In such embodiments, the processor may continue HARQ protocol operationacross the first and second BWPs. In certain embodiments of the firstapparatus, different ones of the active BWPs are associated withdifferent timing advance groups. In such embodiments, the processor maymaintain multiple timing advance loops for the serving cell, each timingadvance loop associated with a different one of the timing advancegroups.

Disclosed herein is a first method for efficient management of multipleactive BWPs. The first method may be performed by a UE, such as theremote unit 105, the UE 205, and/or the user equipment apparatus 600.The first method includes communicating with a serving cell usingmultiple active BWPs for the serving cell. Here, the serving cell isconfigured with multiple configured grants, each active BWP configuredwith one of the multiple configured grants. The first method includesreceiving an indication from a base unit of which configured grants areto be used upon a change to the multiple active BWPs and selectivelyactivating a configured grant in response to a change to the multipleactive BWPs.

In some embodiments, the indication is received in a MAC CE. In suchembodiments, the MAC CE may include a bitmap. Here, each bit of thebitmap may indicate whether a configured grant is to be activated ordeactivated. In certain embodiments, a number of active BWPs is greaterthan a number of activated configured grants. In some embodiments, thefirst method includes receiving an indication to transition to aninactive state and deactivating all active BWPs of the serving cellexcept a single BWP, the single BWP being one of an initial BWP and adefault BWP.

In various embodiments, the change to the multiple active BWPs includesactivating a BWP, deactivating a BWP, or switching an active BWP of theserving cell. In some embodiments, the first method includes receivingan indication to switch an active BWP, wherein the indication to switchan active BWP and the indication of which configured grants are to beused are included in the same message.

In some embodiments, the first method includes supporting a plurality ofservices, each service associated with a different active BWP. Incertain embodiments, the multiple active BWPs are selected from a set ofconfigured BWPs of the serving cell. In such embodiments, the firstmethod may include mapping one or more logical channels to each of themultiple configured BWPs and prioritizing data from the logical channelsfor transmission on an uplink BWP.

In some embodiments, the first method includes checking a pathlosstrigger condition in response to the change to the multiple active BWPsand reporting power headroom information for each of the multiple activeBWPs. In such embodiments, checking the pathloss trigger condition inresponse to the change to the multiple active BWPs comprises checking apathloss trigger condition for subset of the active BWPs.

In certain embodiments, the change to the multiple active BWPs includesswitching a first BWP for second BWP. In such embodiments, checking thepathloss trigger condition in response to the change to the multipleactive BWPs may include: taking a first pathloss measurement on thefirst BWP, taking a second pathloss measurement on the second BWP,calculating a pathloss difference using the first pathloss measurementto the second pathloss measurement, and triggering a power headroomreport if the path loss difference is more than a threshold amount.

In some embodiments, the serving cell is a reference serving cell. Insuch embodiments, the first method may include receiving a pathlossreference linking parameter that links an active downlink BWP to anactive uplink BWP and estimating a pathloss value for the active uplinkBWP using the linked active downlink BWP. In certain embodiments, thelinked active downlink BWP is one of an initially active downlink BWPwithin the reference serving cell and a default downlink BWP within thereference serving cell.

In certain embodiments, the first method includes configuring a HARQentity for each active BWP of the serving cell, each HARQ entitymaintaining a set of parallel HARQ processes. In some embodiments, thefirst method includes configuring a single HARQ entity for all activeBWP of the serving cell. In such embodiments, the single HARQ entity isassociated with a plurality of HARQ processes, wherein the plurality ofHARQ processes are shared across the active BWPs.

In certain embodiments, the change to the multiple active BWPs comprisesswitching a first BWP for a second BWP. In such embodiments, the firstmethod may include continuing HARQ protocol operation across the firstand second BWPs. In certain embodiments, different ones of the activeBWPs are associated with different timing advance groups. In suchembodiments, the first method may include maintaining multiple timingadvance loops for the serving cell, each timing advance loop associatedwith a different one of the timing advance groups.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprising: a transceiver thatcommunicates with a serving cell; and a processor coupled to thetransceiver, the processor configured to cause the apparatus to: receivea configuration for a plurality of bandwidth parts (“BWPs”) for theserving cell, wherein multiple BWPs are simultaneously active;communicate with a serving cell using the multiple active BWPs, whereincommunicating using multiple active BWPs comprises concurrentlyreceiving and/or transmitting data on each of the multiple active BWPs;receive a configuration for multiple configured grants for the servingcell, wherein each of the multiple active BWPs is configured with one ofthe multiple configured grants; configure a separate Hybrid AutomaticRepeat Request (“HARQ”) entity for each active BWP of the serving cell,each HARQ entity maintaining a set of parallel HARQ processes; receive afirst indication to change a set of active BWPs; receive a secondindication from a base unit of which configured grants are to be used inresponse to the change to the set of active BWPs, wherein the secondindication comprises a bitmap, each bit of the bitmap indicating whethera configured grant is to be activated or deactivated, wherein the firstindication to change a set of active BWPs and the second indication ofwhich configured grants are to be used are included in the same message;and selectively activate a configured grant in response to the change tothe set of active BWPs, wherein activating the configured grant inresponse to the change to the set of active BWPs comprises activating aconfigured grant for a previously deactivated BWP.
 2. The apparatus ofclaim 1, wherein the first and second indications are received in amedium access control (“MAC”) control element (“CE”).
 3. The apparatusof claim 1, wherein the change to the set of active BWPs comprises oneof: activating, deactivating, or switching an active BWP of the servingcell.
 4. The apparatus of claim 1, wherein a number of active BWPs isgreater than a number of activated configured grants.
 5. The apparatusof claim 1, wherein the apparatus supports a plurality of services, eachservice associated with a different active BWP.
 6. The apparatus ofclaim 1, wherein the multiple active BWPs are selected from a set ofconfigured BWPs of the serving cell, wherein the processor is furtherconfigured to cause the apparatus to: map one or more logical channelsto each of the multiple configured BWPs; and prioritize data from thelogical channels for transmission on an uplink BWP.
 7. The apparatus ofclaim 1, wherein the processor is further configured to cause theapparatus to: receive an indication to transition to an inactive state;and deactivate all active BWPs of the serving cell except a single BWP,the single BWP being an initial BWP or a default BWP.
 8. The apparatusof claim 1, wherein the processor is further configured to cause theapparatus to: check a pathloss trigger condition in response to thechange to the set of active BWPs; and report power headroom informationfor each active BWPs.
 9. The apparatus of claim 8, wherein, to check thepathloss trigger condition in response to the change to the set ofactive BWPs, the processor is further configured to cause the apparatusto check a pathloss trigger condition for subset of the active BWPs. 10.The apparatus of claim 8, wherein the change to the set of active BWPscomprises switching a first BWP for second BWP, wherein, to check thepathloss trigger condition in response to the change to the set ofactive BWPs, the processor is further configured to cause the apparatusto: take a first pathloss measurement on the first BWP; take a secondpathloss measurement on the second BWP; calculate a pathloss differenceusing the first pathloss measurement to the second pathloss measurement;and trigger a power headroom report if the path loss difference is morethan a threshold amount.
 11. The apparatus of claim 1, wherein theserving cell is a reference serving cell, wherein the processor isfurther configured to cause the apparatus to: receive a pathlossreference linking parameter that links an active downlink BWP to anactive uplink BWP, and estimate a pathloss value for the active uplinkBWP using the linked active downlink BWP.
 12. The apparatus of claim 11,wherein the linked active downlink BWP is an initially active downlinkBWP within the reference serving cell or a default downlink BWP withinthe reference serving cell.
 13. The apparatus of claim 1, wherein thechange to the set of active BWPs comprises switching a first BWP for asecond BWP, wherein the processor is configured to cause the apparatusto continue HARQ protocol operation across the first and second BWPs.14. The apparatus of claim 1, wherein different ones of the active BWPsare associated with different timing advance groups.
 15. The apparatusof claim 14, wherein the processor is further configured to cause theapparatus to maintain multiple timing advance loops for the servingcell, each timing advance loop associated with a different one of thetiming advance groups.
 16. A method comprising: receiving aconfiguration for a plurality of bandwidth parts (“BWPs”) for theserving cell, wherein multiple BWPs are simultaneously active;communicating with a serving cell using multiple active BWP for theserving cell, wherein communicating using multiple active BWPs comprisesconcurrently receiving and/or transmitting data on each of the multipleactive BWPs; receiving a configuration for with multiple configuredgrants for the serving cell, wherein each of the multiple active BWPs isconfigured with one of the multiple configured grants; configuring aseparate Hybrid Automatic Repeat Request (“HARQ”) entity for each activeBWP of the serving cell, each HARQ entity maintaining a set of parallelHARQ processes; receiving a first indication to change a set of activeBWPs; receiving a second indication from a base unit of which configuredgrants are to be used in response to the change to the set of activeBWPs, wherein the second indication comprises a bitmap, each bit of thebitmap indicating whether a configured grant is to be activated ordeactivated, wherein the first indication to change a set of active BWPsand the second indication of which configured grants are to be used areincluded in the same message; and selectively activating a configuredgrant in response to the change to the set of active BWPs, whereinactivating the configured grant in response to the change to the set ofactive BWPs comprises activating a configured grant for a previouslydeactivated BWP.